# Anatomy & Folder Structure

> Supacharger uses four ownership classes. The colours below are labels as well as visual cues, so the tree remains understandable without colour.

# Anatomy & Folder Structure

Supacharger uses four ownership classes. The colours below are labels as well as visual cues, so the tree remains understandable without colour.

  Core exact
  Merge managed
  Forward only
  Developer owned

## Reading the tree

**Core exact** paths are copied from the immutable Core lock and must be byte-identical. **Merge managed** files have a shared contract but retain application values and dependencies. **Forward only** paths are permanent histories: add new migrations, never replace an installed one. **Developer owned** files survive every Core update.

`src/supacharger.config.ts` supplies application values and is checked against the exact `SupachargerConfig` type. Managed forms render stable semantic `sc-*` classes; their dimensions, colours, radii, typography, spacing and layout live in the developer-owned stylesheets under `src/styles/`.

The CLI reads `.supacharger/managed-files.json`, previews each ownership action, preserves developer paths, runs the declared checks and advances `.supacharger/core-lock.json` only after the exact contract passes.

## Naming

Use lowercase kebab-case for files and folders, PascalCase for React component names, and route groups such as `(supacharger)` and `(project)` to separate ownership without changing public URLs.